-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDRP-1149_fix_validation_error #416
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me Anne. However I cannot approve my own PR.
assert pd.api.types.is_integer_dtype(dumy_data["col1"].dtype), "col1 should be of integer type" | ||
assert pd.api.types.is_string_dtype(dumy_data["col2"].dtype), "col2 should be of string type" | ||
assert pd.api.types.is_float_dtype(dumy_data["col3"].dtype), "col3 should be of float type" | ||
assert pd.api.types.is_datetime64_any_dtype(dumy_data["col4"].dtype), "col4 should be of datetime type" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ive never used any pd.api.types.is
... before, fancy. And it passes, so great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To address the warning created by the removal of my previous "fix", I created ticket RDRP-1154.
Pull Request submission
Fixes error described here https://jira.ons.gov.uk/browse/RDRP-1149 with the removal of a previous fix. Within the aforementioned ticket I suggest the the second issue is addressed in a different PR due to the urgency of the issues this problem is causing.
Closes or fixes
Closes #
Code
Documentation
Any new code includes all the following forms of documentation:
Args
andreturns
for all major functionsData
Testing
Peer Review Section
requirements.txt
Final approval (post-review)
The author has responded to my review and made changes to my satisfaction.
Review comments
Insert detailed comments here!
These might include, but not exclusively:
that it is likely to interact with?)
works correctly?)
Your suggestions should be tailored to the code that you are reviewing.
Be critical and clear, but not mean. Ask questions and set actions.